Preserve unemitted remote video timing entries across batch emissions#3179
Merged
hensmi-amazon merged 1 commit intomainfrom Mar 9, 2026
Merged
Preserve unemitted remote video timing entries across batch emissions#3179hensmi-amazon merged 1 commit intomainfrom
hensmi-amazon merged 1 commit intomainfrom
Conversation
Remote video timing entries were lost when the signaling+audio batch emitted before the video tile was bound. Unemitted entries now carry over to the next batch. Also prevents duplicate onRemoteVideoAdded calls on resubscribe from creating zombie entries via emittedRemoteVideoGroupIds tracking.
shi-su
approved these changes
Mar 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix some minor reporting bugs with meeting session timing manager.
Issue #: N/A
Description of changes: See above
Testing:
No longer misses quickly added videos or sends empty timing frames.
Can these tested using a demo application? Please provide reproducible step-by-step instructions.
No
Checklist:
Have you successfully run
npm run build:releaselocally?y
Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved?
n
Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved?
n
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.